home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970929-19971216
/
000038_news@newsmaster….columbia.edu _Fri Oct 3 10:57:37 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA28520
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 3 Oct 1997 10:57:37 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA11572
for kermit.misc@watsun; Fri, 3 Oct 1997 10:57:37 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit via PPP under DOS?
Date: 3 Oct 1997 14:57:35 GMT
Organization: Columbia University
Lines: 33
Message-ID: <61314v$bsc$1@apakabar.cc.columbia.edu>
References: <60i3al$8l@gateway.dircsa.org.au> <60km6a$jsb@gateway.dircsa.org.au> <om90wf99m1.fsf@tees.cs.ualberta.ca>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:7805
In article <om90wf99m1.fsf@tees.cs.ualberta.ca>,
Vladimir Alexiev <vladimir@cs.ualberta.ca> wrote:
: In article <60km6a$jsb@gateway.dircsa.org.au>
: arthur@gateway.dircsa.org.au (Arthur Marsh) writes:
:
: > "check tcp" only determines whether support is compiled in.
: > I did the following in my MSCUSTOM.INI to have a single configuration for
: > both serial and IP connections:
: >
: > set port tcp/ip <ip-address>
: > if success forward passedserial
:
: I think that this will always succeed, because the actual connection is only
: attempted when CONNECT is issued. You should check "if success" after
: CONNECT, and if it's failed eventually examine \v(tcpip_status).
:
There is actually a better way. The way MS-DOS Kermit is structured, as
Vladimir points out, SET PORT TCP merely declares the name of the host to be
connected to, but otherwise does nothing. Various other commands like
CONNECT open the connection if it is not yet open. But of course you don't
want to use CONNECT in a script, because then the script loses control.
Another command also opens the connection if it is not open, but does nothing
more:
PAUSE 0
(or "pause" anything-else"). So a common practice is to define a TELNET
macro like this:
DEFINE TELNET SET PORT TCP \%1, PAUSE 0, IF SUCCESS CONNECT
- Frank